2. EL 7
  3. openafs-1.6-sl
  4. vos_copy(1)

Scroll to navigation

VOS_COPY(1) AFS Command Reference VOS_COPY(1)

NAME

vos_copy - Make a copy of a volume

SYNOPSIS

vos copy [-id] <volume name or ID of source>
[-fromserver] <machine name for source>
[-frompartition] <partition name for source>
[-toname] <volume name for new copy>
[-toserver] <machine name for destination>
[-topartition] <partition name for destination>
[-offline] [-readonly] [-live] [-cell <cell name>]
[-noauth] [-localauth] [-verbose] [-encrypt] [-noresolve]
[-help]

vos cop [-i] <volume name or ID of source>
[-froms] <machine name for source>
[-fromp] <partition name for source>
[-ton] <volume name for new copy>
[-tos] <machine name for destination>
[-top] <partition name for destination>
[-o] [-r] [-li] [-c <cell name>]
[-noa] [-lo] [-v] [-e] [-nor]
[-h]

DESCRIPTION

The vos copy command makes a copy of a volume with a new name. It is equivalent to vos dump followed by vos restore, but doesn't require the volume be stored locally by the client.

CAUTIONS

Currently, the maximum quota for a volume is 2 terabytes (2^41 bytes). Note that this only affects the volume's quota; a volume may grow much larger if the volume quota is disabled. However, volumes over 2 terabytes in size may be impractical to move, and may have their size incorrectly reported by some tools, such as fs_listquota(1).

OPTIONS

[-id] <volume name or ID>
Specifies either the complete name or volume ID number of a read/write volume.
[-fromserver] <machine name for source>
Identifies the file server machine where the source volume resides. Provide the machine's IP address or its host name (either fully qualified or using an unambiguous abbreviation). For details, see vos(1).
[-frompartition] <partition name for source>
Names the partition where the source volume resides. Provide the full partition name (for, example, /vicepa) or one of the abbreviated forms described in vos(1).
[-toname] <volume name for new copy>
The complete name of the new volume to create.
[-toserver] <machine name for destination>
Identifies the file server machine to which to copy the volume. Provide the machine's IP address or its host name (either fully qualified or using an unambiguous abbreviation). For details, see vos(1).
[-topartition] <partition name for destination>
Names the partition to which to copy the volume. Provide the full partition name (for, example, /vicepa) or one of the abbreviated forms described in vos(1).
Leaves the new volume flagged as off-line in the volume database.
Flags the new volume as read-only in the volume database.
Copies the live volume without cloning. This is normally not necessary and causes the volume to be kept locked for longer than the normal copy mechanism.
Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see vos(1).
Assigns the unprivileged identity "anonymous" to the issuer. Do not combine this flag with the -localauth flag. For more details, see vos(1).
Constructs a server ticket using a key from the local /usr/afs/etc/KeyFile file. The vos command interpreter presents it to the Volume Server and Volume Location Server during mutual authentication. Do not combine this flag with the -cell argument or -noauth flag. For more details, see vos(1).
Produces on the standard output stream a detailed trace of the command's execution. If this argument is omitted, only warnings and error messages appear.
Encrypts the command so that the operation's results are not transmitted across the network in clear text. This option is available in OpenAFS versions 1.4.11 or later and 1.5.60 or later.
Shows all servers as IP addresses instead of the DNS name. This is very useful when the server address is registered as 127.0.0.1 or when dealing with multi-homed servers. This option is available in OpenAFS versions 1.4.8 or later and 1.5.35 or later.
Prints the online help for this command. All other valid options are ignored.

OUTPUT

This command has no output unless "-verbose" is specified or there is an error.

EXAMPLES

The following example makes a verbose copy of the "test" volume named "test2" in the cell "localcell". The volume and copy both reside on "/vicepa" of "server1".

   % vos copy test server1  a test2 server1 a -cell localcell -verbose
   Starting transaction on source volume 536870921 ... done
   Allocating new volume id for clone of volume 536870921 ... done
   Allocating new volume id for copy of volume 536870921 ... done
   Cloning source volume 536870921 ... done
   Ending the transaction on the source volume 536870921 ... done
   Starting transaction on the cloned volume 536870926 ... done
   Setting flags on cloned volume 536870926 ... done
   Getting status of cloned volume 536870926 ... done
   Creating the destination volume 536870927 ... done
   Setting volume flags on destination volume 536870927 ... done
   Dumping from clone 536870926 on source to volume 536870927 on destination ... done
   Ending transaction on cloned volume 536870926 ... done
   Starting transaction on source volume 536870921 ... done
   Doing the incremental dump from source to destination for volume 536870921 ...  done
   Setting volume flags on destination volume 536870927 ... done
   Ending transaction on destination volume 536870927 ... done
   Ending transaction on source volume 536870921 ... done
   Starting transaction on the cloned volume 536870926 ... done
   Deleting the cloned volume 536870926 ... done
   Ending transaction on cloned volume 536870926 ... done
   Created the VLDB entry for the volume test2 536870927
   Volume 536870921 copied from server1 /vicepa to test2 on server1 /vicepa

PRIVILEGE REQUIRED

The issuer must be listed in the /usr/afs/etc/UserList file on the machine specified with the -server argument and on each database server machine. If the -localauth flag is included, the issuer must instead be logged on to a server machine as the local superuser "root".

SEE ALSO

vos(1), vos_clone(1), vos_move(1)

COPYRIGHT

Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com>

This documentation is covered by the BSD License as written in the doc/LICENSE file. This man page was written by Jason Edgecombe for OpenAFS.

2019-10-22 OpenAFS